Using Zero Configuration with Automatic Update
Zero Configuration is typically used in combination with the Automatic Update feature, described in detail in HTTP/S-Based Provisioning using the Automatic Update Feature. In such a setup, the Zero Configuration process begins first and only after it completes (successfully or not), does the Automatic Update process begin.
The typical method for using Zero Configuration with Automatic Update is described below. However, your specific deployment architecture may require some adjustments to the method in order to suit your requirements.
|
a.
|
The non-configured device connects to the Redirect server. |
|
b.
|
The Redirect server redirects the device to the URL of the provisioning server. |
|
c.
|
The provisioning server responds with the CLI or ini configuration file that contains configuration settings for the Automatic Update mechanism. An example of a CLI configuration file is shown below: |
automatic-update
auto-firmware http://www.company.com/device.cmp
call-progress-tones http://www.company.com/call_progress.dat
startup-script http://company.com/startup/<MAC>
For CLI-based configuration, the advantage of using the startup-script file over the cli-script file for initial configuration is that it overwrites all existing configuration on the device, thus making the configuration process independent of the device's current configuration.
When provisioning the device based on MAC address (e.g., startup-script http://company.com/startup/<MAC>), although the device connects to the network with the WAN port, the name of the file on the provisioning server must use the LAN MAC address.
|
d.
|
Once connection is established with the provisioning server, the device downloads the Startup Script file or ini file (in the 200 OK response from the provisioning server). |
|
e.
|
Zero Configuration is now considered complete. |
|
a.
|
The device attempts to download the files from the URLs (on the provisioning server) according to the Automatic Update settings. The method for connecting to the provisioning server(s) and for determining whether the file(s) must be downloaded is described in Querying Provisioning Server for Updated Files. The order of the files downloaded by the device is described in File Download Sequence. |
|
b.
|
If the Startup script file or ini file was downloaded, the device resets to activate the new configuration. |